The public unscoped 'guardex' name can conflict with existing npm packages. This keeps the GuardeX brand and gx/guardex CLI commands intact while switching publication/install surfaces to a conflict-safe scoped package name.\n\nUpdated install/docs prompts, package metadata, and tests so self-update checks and setup guidance consistently reference the scoped npm identity.

Constraint: CLI command UX must stay gx-first with legacy musafety aliases intact\nRejected: Keep unscoped guardex package name | collision risk at publish/install time\nConfidence: high\nScope-risk: narrow\nReversibility: clean\nDirective: Keep bin command names stable; only package identity changed for npm distribution safety\nTested: npm test\nTested: node --check bin/multiagent-safety.js\nTested: npm pack --dry-run\nNot-tested: live npm publish/install from registry